NetNews Offline 2/NetNews Offline Volume 2.iso/news/comp/sys/amiga/hardware-part1/182

Text File | 1996-08-05 | 5.8 KB | 134 lines

Newsgroups: comp.sys.amiga.hardware
Path: netcom.com!vjl
From: [e-mail] (Vince LaMonica)
Subject: Re: Serious 2000HD boot problems
Message-ID: <[e-mail]>
Reply-To: [e-mail] (Vince LaMonica)
Organization: A2HD/040/16F/2S/2C/540
X-Newsreader: TIN [version 1.2 PL2]
References: <[e-mail]> <[e-mail]>
Date: Wed, 3 Jan 1996 17:39:43 GMT
Sender: [e-mail]

Richard Gordon Singles ([e-mail]) really typed:
 [I typed:]
{ >I seem to be having a fairly serious problem with my rev4.4 B2000-CR. Due
{ >to a recent upgrade (a 28mhz PP&S040 board), I've spent the last 2 months
{ >in limbo. :( I thought I had finally got things stablized, but it appears
{ >I haven't.
{ >
{ >
{ >gvpscsi.device: unit 006
{ >unexpected status $40/$00
{ >

{ I think the gvpscsi.device: unit 006 indicates the hard drive at SCSI
{ address six is the problem, or at least it was in this instance. Start
{ looking here first.

     Yep, that is where I am looking (though I just changed my HD to unit
     0 a while ago, but haven't come across the above error since then.

{ Someone out there may (Ralph Babel??) may be able to tell you just
{ what kind of errors these numbers indicate, but my first guess would
{ be termination problem.  Follow the SCSI termination rules. If you doubt
{ the integrity of the SCSI ribbon cable itself replace it.  3cm worth of
{ ribbon cable should be cheap--even if you by new connectors (IDCs).

     I've followed the SCSI termination rules (and that lone exception
     re: an internal 3cm cable connected to one device). I've even
     clipped off the GVP 4008's paks so that my ZIP (external) would be
     correctly placed in the SCSI chain. The GVP board and HD are less
     than 8 months old.

{ The second idea I had (My brain hurts....)

     :)

{ was that maybe the reselection
{ for the ZIP drive is in the wrong setting.  I don't have a ZIP drive,
{ but I remember reading somehere that this was even more important on
{ removable-medium drives than on fixed-disk hard drives.

     Umm..ok..I'm not sure what "reselection" is, so if you could
     enlighten me further, I'd appreciate it. :)


{ Change your Boot drive/partition to SCSI address 0.  This will mean
     [...]
{ a bootable drive.  It also would help to make sure the RESELECTION and
{ LAST LUN (logical unit number) flags for this drive are set.

     Ok, did that, but no change (read on for latest info...) Again,
     though, what is "reselection"?

{ Maybe you broke off more than the SCSI controller's termination
{ resistor packs.....  If it was me, I would have de-soldered them and
{ put in sockets. At least this would let you test the hard drive
{ on it's own and then add the ZIP drive to a stable system....

     I was very careful when clipping the paks off..didn't want to take a
     chance with a soldering iron though. :(

{ Maybe you could try re-installing your system software from scratch?
{ Could it be that the PP&S040 board needs it's own (custom)
{ 68040.library?  Some accelerators choke on C='s version.

     A friend has the same board (though with a 33mhz 040) and we both
     have the same PP&S software versions and C= programs (68040.library,
     etc).

{ Maybe all the GURUs are caused by an overheated processor.  I have never
{ seen your particular brand of accelerator up close before, but I know
{ my 33MHz '040 would fry without it's cooling fan/heatsink.  Maybe you
{ need a fan (or a better one?)?

     Perhaps (it does have a fan), but I think the problem is a RAM/disk
     problem (read on for more..)


     Here is what is happening now:

     If I set the jumpers on the PP&S040 board so that 0 MB of RAM is
     AutoConfiged *and* don't use AddMem to add any of the memory to
     32bit ranges, I am basicly ok. I can reboot (warm and cold) and
     actually get to the WorkBench. But, if I AutoConfig 2 MB and run
     AddMem to configure the remaining 2 MB into 32bit range, I can only
     boot once without major problems. Once I am running, I get CRC
     errors when DLing every 8192 bytes (8K) and random GURUs and
     lockups. If I configure 2 MB into AutoConfig range and DON'T use
     AddMem to add the remaining 2 MB into 32bit range, then I don't have
     the booting problems, but I still get the CRC errors and the
     occasional lockup. The booting problems occur after I've had one
     successful boot: A reboot (or power up/down) will spin my drive and
     that's it; a 2nd attempt will grind away at the drive and may come
     up to a requestor saying my DH0: partition isn't validated..if I
     click on cancel, sometimes I freeze, sometimes it continues to boot
     and my DH0: becomes magicly available (ie: validated) again.

     So basicly, if I don't tell my system about the 4 MB on the 040
     board, it will run fine; if I tell it that there is either 2 MB or 4
     MB of AutoConfig RAM on the board, I get CRC errors (when DLing) and
     random lockups/GURUs. If I put any of the RAM into 32bit range, I
     have major probs trying to boot (boot from floppy won't work via the
     boot menu). I am using the following addmem line:

     System3.1:C/AddMem3.01 >NIL: $8000000 $81FFFFF local priority 6

     (running it without >NIL:, I can see that it does indeed have no
     problems with assigning the RAM at those locations).

     I am using a DMA mask of: 0xfffffffe with a max trans of: 0xffffff
     on my 540MB SCSI Quantum Maverick and a DMA mask of: 0xfffffe and
     the same max trans as above, for my ZIP drive. Using FFS (with
     International Mode on) on the ZIP, and FFS on the HD (w/o
     International mode).

     Thanks for all the suggestions, Richard...and thanks to any more I
     get..I really appreciate your help..! :)


--
[e-mail]   blank.sigblank.sigblank.sigblank.sigblank.sigblank.sigbla
Vince LaMonica   nk.sigblank.sigblank.sigblank.sigblank.sigblank.sigblank.